2015-09-02 - 16728 - Spec - SNC No Work Order Process #SNCProject #sncsup

SPECIFICATIONS 2015-09-02 - Spec - 16728 SNC No Work Order Process

Purpose

Develop a Process for SNC in which there shall not be any Work Orders and the confirmations can be updated to ECC system.

Admin Info

Purpose	SNC No Work Order Process
Requested By	Jeffrey Mau
Spec Created By	Venkat/Adithya
Spec Created Date	09/02/2015
Spec QA by	Venkat/Adithya
Objects
Document Status	Closed - This option is not used in the Simplified WO Process

Estimates

Sl.No	Activity	Estimation in Hours
1	Research
2	Documentation
3	Development/ Config
4	Unit test in DEV
5	Unit test in QUA
6	Other activity
	TOTAL

References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

Documents

[Attach any document(s) received for the requirement(s)]

Spec Changes

[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.	Change Details	Requested By	Requested On	Notes if any

Functional Requirement

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

In Scope:

[List the activities to be included in scope]

Out of Scope:

[Out of scope activities]

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]

Open POs related to SNC Vendors will be downloaded into a CSV file via a daily job. (See Issues for criteria)
This file will be sent to a .NET application via FTP where it will be loaded into a table with no changes. The table will always be truncated before loading the latest data.
Users will use the .NET application to access the selected PO lines. All the phases of the PO Line is displayed in the same row.
Users will be allowed to confirm the remaining phases for Line of that PO (in mass or individually)
At the end of the day, SSIS package generates a PO Confirmation File and the file will be sent to ECC via FTP which is placed in Application Server
A job will be run in ECC to confirm PO Line Phases for the PO Lines from File
Security: Users will only be able to see their own company's POs.

Test Plan
[List test scenarios/cases to be executed here]

Test ID	Test Scenario	Expected Results
SCM1	Full End to End Cycle shall be executed with different PO types NB - Standard NB- TAB Z3NB - TAS with combination of two vendors.	End to End cycle shall be executed be done correctly.Validation Reports- Both files created in ECC (PO Line file) and data in the .Net file should contain ALL records per filter criteria (all open POs) Records loaded in .NET should contain ALL records received from ECC Confirmations in .NET should be reflected in ECC Confirmations.
SCM2	Execute scenarios with multiple cycles to ensure PO statuses are updated correctly in ECC after each receipt from .NET	PO confirmations in ECC after each cycle should be correct.
SCM3	Check the ASN (Booking and Shipping) Files and validate it with and with out work order process	Booking and shipping files shall contain all the information when compared with work order and with out work order.
SCM4	Security check- User will try to enter PO which may or may not be part of their company	No EB POs Work Orders shall be seen in the ML Screen and vice versa

.Net Application testing.

Test ID	Test Scenario	Expected Results
001	Enter PO number and click on Apply	The PO details for the shall be displayed in the grid
002	Update the confirmations for the Phases by flagging and unflagging the check boxes and save	User should be able to check and uncheck the check boxes for the phase completed and the data should be saved to database on Save click
003	Day End Process	User should be able to download the updated confirmations.
004	Ensure all Open PO Lines Received

PO_LINE file Testing

Test ID	Test Scenario	Expected Results
PO_LINE001	Run the PO_LINE file Job 1. ZE updated for all lines of a PO 2. ZE updated for all lines of a PO and any one line updated till ZP 3. ZE updated for all lines of a PO and all lines updated till ZP 4. ZE updated for all lines of a PO and any one line of a PO is deleted. 5. ZB updated for all lines of a PO 6. ZB updated for all lines of a PO and any line updated till ZP 7. ZB updated for all lines of a PO and all lines updated till ZP 8. ZB updated for all lines of a PO and any two lines of a PO is deleted 9. ZE&ZB updated for all lines of a PO 10. ZE&ZB updated for all lines of a PO and any line updated till ZP 11. ZE&ZB updated for all lines of a PO and all lines updated till ZP 12. ZE&ZB updated for all lines of a PO and any two lines of a PO is deleted 13. ZE&ZB updated for all lines of a PO and confirmations updated till ZN with delivery completion indicator. 14. ZE&ZB updated for all lines of a PO and confirmations updated till ZN. 15. ZE&ZB updated for all lines of a PO are updated with ZP. 16. ZE&ZB updated and all lines of a PO are updated till ZP with delivery completion indicator. 17. ZE&ZB updated and all lines of a PO are updated till ZS with delivery completion indicator. 18. ZE&ZB updated and all lines of a PO are deleted.	A file shall be placed in the application server. 1. All lines of the PO shall be there in the Downloaded file. 2. All lines of the PO shall be there in the Downloaded file with ZP updated for that line which for ZP is updated. 3. No Lines of the PO shall be there in the Downloaded file. 4. Excluding the deleted line all lines of the PO shall be there in the downloaded file. 5. All lines of the PO shall be there in the Downloaded file. 6. All lines of the PO shall be there in the Downloaded file with ZP updated for that line which for ZP is updated. 7. No Lines of the PO shall be there in the Downloaded file. 8. Excluding the deleted lines all lines of the PO shall be there in the downloaded file. 9. All lines of the PO shall be there in the Downloaded file. 10. All lines of the PO shall be there in the Downloaded file with ZP updated for that line which for ZP is updated. 11. No Lines of the PO shall be there in the Downloaded file. 12. Excluding the deleted lines all lines of the PO shall be there in the downloaded file. 13. All lines of the PO shall be there in the Downloaded file. 14. All lines of the PO shall be there in the Downloaded file. 15. No Lines of the PO shall be there in the Downloaded file. 16. No Lines of the PO shall be there in the Downloaded file. 17. All lines of the PO shall be there in the Downloaded file. 18. No Lines of the PO shall be there in the Downloaded file.
PO_LINE002	Download the file wide open 1. If any one line of a PO is active (with out delivery completion indicator or deletion) 2. If No Lines of the PO are updated with any phase. 3. If all lines of the PO are updated with all Phases till COM or the PO is closed 4. If All lines of the PO are mix of Open, Delivery complete & Deleted	All the Open POs and its corresponding lines must be downloaded in the file 1. All the Lines of that PO must be downloaded in the file. 2. All the Lines of that PO must be downloaded in the file. 3. No Lines of that PO must be downloaded in the file. 4. All the lines of that PO must be downloaded in the file.

Confirmations Program:

Test ID	Test Scenario	Expected Results
CNF001	Run the confirmations program	The confirmations which are updated from .Net application in the file are to be updated.

Solution Details

[Provide complete technical details for configuration or programming here]
Step 1: Generate the Open PO File from in ECC.

Step 2: Send the Open PO File to .Net Application.

Step 3: Browse the POs and Its lines in .Net Application and update the confirmations.

File 1:

Generate the Open PO File for SNC Vendors
An FTP Script will be developed to place the Active PO File in .Net Server.
This will be run at a scheduled time

Issues

[List Issues / Bugs identified in configuration or development]